home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
os2
/
gigo0714.zip
/
HEADERS.FAQ
< prev
next >
Wrap
Text File
|
1995-07-29
|
3KB
|
93 lines
Q: How do I tell GIGO which headers I want from the messages?
Q: What are KEEP, HIDE, KILL, and RMAIL_KEEP_ALL
A: GIGO uses the KEEP, HIDE, and KILL keywords to determine which headers
to import from the original message. By default, no headers are kept.
If you specify RMAIL_KEEP_ALL, then the default for _email_
is to _KEEP_ all headers.
Be sure to end the header with ":". Most header lines have the ":",
so GIGO is picky on this one. To specify a header that does not use
the colon, simply omit it.
(Clarification: "From " is different from "From:"; both are present
in email messages.)
To KEEP certain headers:
Keep Apparently-to: ; Shows who it's going to
Keep Archive-Name: ; Used in news.answers and elsewhere
Keep Date: ; What date the message was written (orig text)
Keep From: ; Who it's from (highly suggested)
To HIDE (as in, keep them, but hidden in the kludge lines)
Hide Newsgroups: ; What newsgroups the message was posted to
Hide Message-ID: ; Original MSGID from the usenet message
Hide Organization: ; Organization (if any) of the person writing the msg
Hide Subject: ; Full subject line
Hide To:
Hide Received:
Hide Reply-To:
Hide Sender:
Hide In-Reply-To:
Hide Mime-Version:
Hide Content-Type:
Hide Errors-To:
Hide Precedence:
Hide X-To:
Hide X-Sender:
Hide X-Ftn-To:
Hide X-Ftn-From:
Hide X-Resent-By:
Hide X-Admin-Addr:
Hide X-List-Software:
Hide X-Listname:
To KILL (as in, useless info, we don't want it)
Kill Path: ; This field is a USELES field for most gateways
Q: How do I tell GIGO which headers I want to allow my users to create?
Q: What is this ALLOW keyword for?
A: For this, the ALLOW keyword is used. By default, users are allowed
only the "To:" header, so as to tell the gateway where they want the
message to go to. In addition, any header starting with "X-" is allowed,
since those are generally used with various email services.
You may have need to allow users to create and/or override
certain headers, a practical example would be the "Reply-To:" header.
Assuming that you add "ALLOW REPLY-TO:" to your config file,
your users will be able to write a message such as:
+------------------------
|From: User Name, 1:2/3
|To : UUCP, 1:203/2
|Subj: Whatever subject
+------------------------
|To: null@wmeonlin.sacbbx.com
|Reply-To: User.Name@othersite.org
|
| Message body goes here
Q: What if the header is too big for one line?
A: Simple, use ".." on the second line. Ie,
+------------------------
|From: User Name, 1:2/3
|To : UUCP, 1:203/2
|Subj: Whatever subject
+------------------------
|To: null@wmeonlin.sacbbx.com
|Organization: This is going to be a really long Organization
|.. line that will probably not fit into 80 characters or less.
|
| Message body goes here
Note that there is a space after the ".." ; GIGO will not put
anything in by itself - if it needs a space, or a comma,
put it in!